Repository navigation
fix(release): ship Node 24.22.1 with pinned runtime checksums - #72
Merged
Merged
Conversation
4 tasks done
kerdofficial
force-pushed
the
fix/node-24-22-1
branch
from
October 22, 2026 19:53
d701f04 to
532cf20
Compare
Merged
4 tasks done
kerdofficial
force-pushed
the
fix/node-24-22-1
branch
from
October 23, 2026 02:15
532cf20 to
f41aa13
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The packaged runtime, the CI, release and site workflows, the engines floor and the docs move from Node 24.21.0 to 24.22.1.
scripts/package.mjsnow pins the SHA-256 of every release-target Node archive. It still fetches nodejs.org'sSHASUMS256.txtand fails if that list disagrees with any pin. The release smoke test asserts the bundled runtime reports v24.22.1.Why
Node 24.22.1 is the October 2026 security release, and release archives shipped 24.21.0. Packaging also trusted a checksum list fetched over TLS at build time, while the pins are now reviewed in source. Note that the
SHASUMS256.txtsignature was not GPG-verified here because gpg was not available.Checklist
pnpm checkpasses locallyProof:
pnpm test:packagingpassed (13 passed, 6 skipped) and vitest passed (1020). The six pins match https://nodejs.org/dist/v24.22.1/SHASUMS256.txt. No packaging, signing or publishing was run.